[Solved] Favorite File System

I'm looking for file system suggestions for a data server which I'm reworking right now due to failures from my first selection.
I used Ext3 which worked for a year+ and has now degraded to the point of being unusable. I'm wondering if any one has experience with linux based data servers and could suggest a file system with journaling and tools that can be used as is.
With Ext3 you have to drop the file system back to Ext2 to work on it...or at least that is what I have read and treated as such.
Any ideas? Experience based suggestions?
(software raid will be used)
Last edited by jduped (2009-06-19 06:46:06)

Thanks for the input guys...I've never used jfs but looks like a good idea
I was reading about it in the beginners guide. and the wiki page on here.
Tryiel interesting way of laying out your partitions with all those mounts are you using lvm? or a few separate drives?
To further on my issue.
The drives are accessible, but read times are unacceptable and with media files they often freeze and lock. The info I found said to degrade ext3 to ext2 then run some of the tools on it. I got an external drive 1TB that I'm dumping all the drives off with then I'm going to rebuild with fresh formats and os. I just didn't want to run into this again.
I think in the long run ext4 has some promise.
Thanks again

Similar Messages

[SOLVED] Ring file-system for a surveillance server?

In my home, I have a (almost) dedicated (Arch-32) computer to use as a surveillance server. It continuously fetches video from a IP camera using motion and saving various GB of images and videos. Obviously, I have to manually delete older videos when the disk is getting full, but it would be better to have some kind of file-system that overrides the older files with the newer ones when it gets full.
Is there anything like that? Any recommendations?
Thanks!
PS: If your suggestion/solution could only delete videos (not images), better.
Last edited by sironitomas (2011-03-12 04:06:12)

limaunion wrote:
One possiblity is to schedule a daily cron job with something like this:
find /home/videos/ -mindepth 2 -cmin +2880 -exec rm -rf {} \;
In this case cmin=2880 (in minutes) equals 48 hours; 'man find' is your friend
Regards (from baires)
LU
Gracias! I didn't know about find's cmin, it is a great option. Exec gave me some problems so I ended up using more than one command. This is the script actually:
find /home/user/videos -cmin +4320 > temp
rm `cat temp | grep avi`
rm temp
The only thing bad about it, is that when find doesn't produce any output, rm shows a error message because there are no arguments. I know that's not the best way, but it works.
Any recommendation is accepted.
Thanks!
Last edited by sironitomas (2011-03-12 04:05:38)

[SOLVED]Root file system changed

I'm currently using ArchLinux
I'm not sure what went wrong, but now when I login as root and "cd" I don't see the root file system. Instead i see
[root@aspect ~]# ls -al
total 36
drwxr-x--- 7 root root 4096 Apr 13 16:29 .
drwxr-xr-x 17 root root 4096 Apr 13 08:18 ..
-rw------- 1 root root 2849 Apr 13 16:27 .bash_history
drwxr-xr-x 2 root root 4096 Apr 13 10:35 .config
drwx------ 3 root root 4096 Apr 13 10:34 .dbus
-rw------- 1 root root 49 Apr 13 10:35 .directory
drwxr-xr-x 3 root root 4096 Apr 13 10:34 .kde4
drwxr-xr-x 3 root root 4096 Apr 13 10:35 .local
drwx------ 3 root root 4096 Apr 13 16:29 .nv
If I cd to ".." I can see the root file system from there.
Also When I drag files into terminal, it can't locate them. I Used a java folder I had in downlaods as an example. But it's like this everywhere.
[aspect@aspect ~]$ file:///home/aspect/Downloads/jre bash: file:///home/aspect/Downloads/jre: No such file or directory
Last edited by aspectratio (2015-04-13 22:05:33)

ewaller wrote:
aspectratio wrote:I've already done all of this. What makes you think I was running KDE as root?
drwxr-xr-x 3 root root 4096 Apr 13 10:34 .kde4
Sometime today a hidden directory containing kde files was created in the /root being owned by root. That's how
So the problem here is I came from debian. And aparently there when you cd as root, it will bring you to the atual file system.
Fair enough.
I was told to edit /etc/passwd and change the root dir to just / from /bin/bash
Now I can no longer login as root. I will try to boot recue mode and chroot into the system to fix the file.
That would be the way to fix it. You may not need to actually chroot, just mount the root partition at /mnt and edit /mnt/etc/passwd.
As to not running desktop environments as root -- it is a pet peeve of mine. I am not saying this about you, you understand the issue; but I have had arguments with people in the past about not running GUI DEs as root, and them insisting on it being their machines and they can do what they want. They are absolutely correct. But they can also fend for themselves.
Edit: If you do have another user in wheel, and if wheel can gain root privileges, just log in as that user and use sudo to fix it.
Yeah it's a security risk.
I've fixed the file. But I'm just not sure why I can't drag and drop paths anymore. It apears as though it's not a common thing anyways.

[SOLVED]root file system partition too small

O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Last edited by rsw (2008-10-16 00:52:02)

rsw wrote:
O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Yep, your home partition is directly after the root partition, so what I suggested should work, however, give good consideration to the size of each, considering you don't have another drive (according to df) to use for storage. Personally, I only have 12GB on my home partition (after resizing) and now have 23GB on root.
Here's mine.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb3 22864180 7438764 14503608 34% /
none 517648 548 517100 1% /dev/shm
/dev/sdb4 11897496 5947088 5470708 53% /home
/dev/sdb1 38888 22534 14346 62% /boot
/dev/sda1 155059036 37878624 109365872 26% /media/thevault
/dev/sdc1 116294120 84739460 25693748 77% /media/music
Last edited by Execute_Method (2008-10-14 12:53:41)

SOLVED: kernel loads, but doesn't have a root file system

Hi,
The system is an Asus X202E. It does UEFI and has a GPT partition system. I've gotten through that part. And it is clear to me that the kernel loads.
It's the next step that's giving me grief. I've tried this with two bootloaders: gummiboot and rEFInd.
With gummiboot, the kernel panics because it can't mount the root file system. With rEFInd, it gets to the intial ramdisk and then drops me to a shell, apparently because the root file system is set to null, and it obviously can't mount that as "real root".
Here is what I posted on the Arch mailing list, documenting that I have indeed specified the correct root (I'm copying this from the email, eliding the unfortunate line wraps):
bridge-live# cat /boot/loader/entries/arch.conf
Title Arch Linux
linux /vmlinuz-linux
initrc /initramfs-linux.img
options root=PARTUUID=d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
bridge-live# ls -l /dev/disk/by-partuuid
total 0
lrwxrwxrwx 1 root root 10 Apr 15 19:26 0ab4d458-cd09-4bfb-a447-5f5fa66332e2 -> ../../sda6
lrwxrwxrwx 1 root root 10 Apr 15 19:26 3e12caeb-1424-451c-898e-a4ff05eab48d -> ../../sda7
lrwxrwxrwx 1 root root 10 Apr 15 19:26 432a977b-f26d-4e75-b9ee-bf610ee6f4a4 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 15 19:26 95a1d2c2-393a-4150-bbd2-d8e7179e7f8a -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 15 19:26 a4b797d9-0868-4bd1-a92d-f244639039f5 -> ../../sda4
lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8
lrwxrwxrwx 1 root root 10 Apr 15 19:26 ed04135b-bd79-4c7c-b3b5-b0f9c2fe6826 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 15 19:26 f64f82a7-8f2b-4748-88b1-7b0c61e71c70 -> ../../sda5
The root partition is supposed to be /dev/sda8, that is:
lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8
So the correct PARTUUID followed by the one I have specified in
arch.conf is:
d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
I'm guessing that this is really the same problem with both gummiboot and with rEFInd, but don't really know. It's clear to me that the initrd is not being correctly constructed. So I removed /etc/mkinitcpio.conf and did, as per the Arch wiki,
pacman -Syyu mkinitcpio linux udev
No joy.
I don't even know which way to go at this point. If I even knew how to tell it where the real disk is in the initial ram disk shell, that would help. Better of course, would be actually solving the problem.
Thanks!
Last edited by n4rky (2013-04-17 21:41:36)

I have made extremely limited progress on this issue.
My previous attempt to specify the root partition in mkinitcpio.conf was insufficient. Furthermore, this is no place--despite the documentation--for the orthodoxy about using UUIDs rather than the straight /dev/sdx. In my case:
root=/dev/sda8
and run
mkinitcpio -p linux
It still drops me into the shell at boot. I can do
mount /dev/sda8 /new_root/
and exit the shell. It still won't believe it has the root device and drops me back in. I just exit.
At this point, for a very brief moment, things look promising. It appears to be starting normally. Then, gdm.service, NetworkManager.service, and dbus.service all fail to start. There may be others but the screen goes by too quickly. At this point, it hangs trying to initialize the pacman keyring and all I can do is CTRL-ALT-DEL.
It occurred to me that this might extend to the rEFInd configuration and so I modified it to also use /dev/sda8 rather than the UUID, but this made no difference. Trying to boot via gummiboot still yields the previously specified kernel panic.

Root File system is reporting that it's full [SOLVED]

My root file system is reporting as full, and I'd like some ideas on how to track the problem. I've tried a number of things like searching for the largest directory, searching for the largest file, and all that jazz. I'm obviously missing something. /dev/sda3 should be at 50%.
One note. The computer started what seemed like normal today. I converted my second hard drive to ext4, rebooted, and started to notice that things that needed the /tmp directory couldn't start. I made some quick space to get operational by removing 56M of stuff from pacman's cache, but that's a quick hack. I don't know if this is related or not. I am running testin

skottish wrote:
MoonSwan wrote:
You're a dork who solved this issue and will know better next time. How is this a bad thing? I'm sure someone around here has done worse Skottish, so don't feel too stupid. (Won't name names but I'm sure as well that I've done worse somewhere...)
In the meantime, while you're down...*bonks skottish with the dork-stick*
Thanks for the kind words MoonSwan.
This happened because of the way my system is set up. I have rsync making backups of /home and /etc to /backup on close. It turns out that rsync created the /backup directory instead of using the existing one. Why? Because /dev/sdb1 wasn't mounted when I restarted after the conversion. Doh!
no shame in that. i totally freaked out once when i was still in school because i couldn't find a paper that was due. turned out i had /home unmounted when i saved the file, but had /home mounted when i went looking for it.
it was hiding under the mounted filesystem the whole time!

[SOLVED] Systemd stuck at "Starting File system check"

Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)

jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21)

[SOLVED] Wince Exception 'Data Abort' (0x4) for gwes.dll with ROM based file system??

Hello friends,
Previously, I was using RAM and ROM based file system and my device was booting correctly. Now, I made only one change related to ROM based file system. When I selected this ROM based file system and try to boot the device.... I got the exception and the
logs are ----
3321 PID:400002 TID:410002 SetOpp: choosing AM335X_REV_ES2_1
3321 PID:400002 TID:410002 SetOpp to 3
3331 PID:400002 TID:590002 OALIoCtlHalInitRTC: Initializing RTC
3331 PID:400002 TID:590002 RTC_SetTime() = 2006.01.01 12:00:00.000
3480 PID:400002 TID:930006 ECC TYPE is BCH 8 bit
3481 PID:400002 TID:930006 8Bit NAND device
4835 PID:400002 TID:930006 CM3: input file [\windows\firmware.bin] is 9932 bytes long
4837 PID:400002 TID:930006 CM3: firmware file read ok!
5037 PID:400002 TID:930006 SDHC: CPU revision 0xffffffff
5181 PID:400002 TID:930006 UCD_INIT: g_Dc.pUsb0Regs->MODE_R = 0x80
5185 PID:400002 TID:930006 CAM3xxOTG::Init DEVCTL 80
5391 PID:400002 TID:930006 UsbPowerModule: 2 DEVCTL = 0x00000081
5664 PID:400002 TID:2df001e Exception 'Data Abort' (0x4): Thread-Id=02df001e(pth=9e451cc8), Proc-Id=00400002(pprc=8219f5e0) 'NK.EXE', VM-active=04510006(pprc=9e4658c0) 'GweUser.exe'
5664 PID:400002 TID:2df001e PC=efd918b8(gwes.dll+0x000118b8) RA=efd918b8(gwes.dll+0x000118b8) SP=ab5ff960, BVA=00000024
1529482 PID:400002 TID:2df001e Exception 'Data Abort' (0x4): Thread-Id=02df001e(pth=9e451cc8), Proc-Id=00400002(pprc=8219f5e0) 'NK.EXE', VM-active=04510006(pprc=9e4658c0) 'GweUser.exe'
1529483 PID:400002 TID:2df001e PC=efd918b8(gwes.dll+0x000118b8) RA=efd918b8(gwes.dll+0x000118b8) SP=ab5ff960, BVA=00000024
PB Debugger The Kernel Debugger has been disconnected successfully.
After giving calibration inputs, I go the above exception and the LCD screen becomes white only... But i only changed the file system from RAM & ROM based file system to ROM based file system....
As, I am trying to find the solution but up to now I am unable to find the solution. I request to provide the appropriate inputs????

Hello Friends,
After using the filter as an environment variable in the .bat file still the issue is not solved.. I can only see the Windows Embedded Compact 7 logo without any icon and toolbar??????
My platform .reg files entries are as -
;; Load Device Manager to start storage driver
#if (defined SYSGEN_FSROMONLY)
[HKEY_LOCAL_MACHINE\init\BootVars]
"Start DevMgr"=dword:1
;; Block driver settings to load at boot phase
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\]
"Profile"="FlashDisk"
"Flags"=dword:1000
;; How to use storage space
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"AutoMount"=dword:1
"AutoPart"=dword:1
"AutoFormat"=dword:1
"PartitionDriver"="mspart.dll"
"MountAsBootable"=dword:1
"Name"="NANDFLASH"
"Folder"="NANDFLASH"
"DefaultFileSystem"="FATFS"
;; Making storage device as a root
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
"MountAsRoot"=dword:1
"MountAsBootable"=dword:1
"MountPermanent"=dword:1
"AutoPart"=dword:1
"AutoFormat"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS\Filters\fsreplxfilt]
"dll"="fsreplxfilt.dll"
"order"=dword:1 ; must be loaded before other filters
#endif
;===============================================================================
and .bat file entries are as -
set SYSGEN_FSREPLXFILT=1
set PRJ_ENABLE_FSEXTREPL=1
set PRJ_ENABLE_FSMOUNTASROOT=1
Where I am missing some thing please tell me???????

[SOLVED] ERROR: Unable to determine the file system type of /dev/root:

:: Running Hook [udev]
:: Triggering uevents...done
Root device '804' doesn't exist.
Creating root device /dev/root with major 8 and minor 4.
error: /dev/root: No such device or address
ERROR: Unable to determine the file system type of /dev/root:
Either it contains no filesystem, an unknown filesystem,
or more than one valid file system signature was found.
Try adding
rootfstype=your_filesystem_type
to the kernelcommand line.
You are now being dropped into an emergency shell.
/bin/sh: can't access tty; job control turned off
[ramfs /]# [ 1.376738] Refined TSC clocksource calibration: 3013.000 MHz.
[ 1.376775] Switching to clocksource tsc
That's what I get when I boot my Arch system. It worked fine for quite a while, but suddenly it ran into an error where the SCSI driver module was corrupt. I fixed it by reinstalling util-linux-ng and kernel26, however, I run into this issue now. http://www.pastie.org/2163181 < Link to /var/log/pacman.log for the month of July, just in case. Yes, I bought a new ATI/AMD Radeon HD 5450 this Saturday, but it seemed to work fine till this broke and it works fine on Ubuntu too, so I suppose we can rule it out.
Last edited by SgrA (2011-07-05 20:45:36)

Autodetection failed on your first image, in both your previous kernel installs:
[2011-07-04 16:14] find: `/sys/devices': No such file or directory
Which means that sysfs was not mounted. You should be able to boot from the fallback image, which does not use autodetect. Figure out why /sys isn't mounted, as well, and fix that.
This is also a somewhat crappy bug in mkinitcpio that lets you create an autodetect image that's useless. It'll be fixed in the next version of mkinitcpio that makes it to core.
Last edited by falconindy (2011-07-04 17:41:19)

A bad scare: root file system recovery [SOLVED]

Hi, everybody,
The trouble began with an odd message: KDE Daemon: new storage detected (hard disk): open in a new window, ignore. Unfortunately, the hard disk in question is statically mounted via /etc/fstab; should have been mounted all along.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide,iocharset=utf8 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide,iocharset=utf8 0 0
/dev/fd0 /mnt/fd0 vfat user,noauto 0 0
/dev/sdb1 swap swap defaults 0 0
/dev/sdb2 / ext3 defaults 0 1
/dev/sdb3 /home ext3 defaults 0 1
#/dev/sda1 /home/alexey/mnt/a ext3 defaults 0 1
It's /dev/sda1, now commented. Real trouble began when I tried to reboot. The kernel told me there's no root file system on sdb2; it checked the disks unsuccessfully, with scary messages about bad device names and device blocks, advised me to use rootfstype=kernel option, etc. sda1 turned out "bad" too. In fallback mode the system booted, but with file systems mounted read only; not much use... Using some recovery disk I commented out the /dev/sda1 line in /etc/fstab on suspicion that sda is the real offender; tried to reboot, without much success, then rebooted again, and something clicked into place; the system is back to normal, but I fear to approach sda1 . What happened? Any suggestion/link is going to be appreciated. It was pure luck; next time it could be much worse.
Edit:
Looks like 'clicked into place' is just the fallback kernel; kernel-related issue? It ran smoothly after the initial upgrade for a couple of weeks.
Edit:
A relevant snippet from kernel.log:
Apr 23 19:52:25 stovepipebox ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
Apr 23 19:52:25 stovepipebox ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
Apr 23 19:52:25 stovepipebox ata2.00: ATAPI: _NEC DVD_RW ND-4550A, 1.06, max UDMA/33
Apr 23 19:52:25 stovepipebox ata2.00: configured for UDMA/33
Apr 23 19:52:25 stovepipebox scsi 1:0:0:0: CD-ROM _NEC DVD_RW ND-4550A 1.06 PQ: 0 ANSI: 5
Apr 23 19:52:25 stovepipebox sata_nv 0000:00:0e.0: version 3.5
Apr 23 19:52:25 stovepipebox ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
Apr 23 19:52:25 stovepipebox ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 16
Apr 23 19:52:25 stovepipebox PCI: Setting latency timer of device 0000:00:0e.0 to 64
Apr 23 19:52:25 stovepipebox scsi2 : sata_nv
Apr 23 19:52:25 stovepipebox scsi3 : sata_nv
Apr 23 19:52:25 stovepipebox ata3: SATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe000 irq 16
Apr 23 19:52:25 stovepipebox ata4: SATA max UDMA/133 cmd 0xe400 ctl 0xe080 bmdma 0xe008 irq 16
Apr 23 19:52:25 stovepipebox ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 23 19:52:25 stovepipebox ata3.00: ATA-6: ST3120827AS, 3.42, max UDMA/133
Apr 23 19:52:25 stovepipebox ata3.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 23 19:52:25 stovepipebox ata3.00: model number mismatch 'ST3120827AS' != '3120827AS '
Apr 23 19:52:25 stovepipebox ata3.00: revalidation failed (errno=-19)
Apr 23 19:52:25 stovepipebox ata3: limiting SATA link speed to 1.5 Gbps
Apr 23 19:52:25 stovepipebox ata3.00: limiting speed to UDMA/133:PIO3
Apr 23 19:52:25 stovepipebox ata3: failed to recover some devices, retrying in 5 secs
Apr 23 19:52:25 stovepipebox ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 23 19:52:25 stovepipebox ata3.00: configured for UDMA/133
Apr 23 19:52:25 stovepipebox ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 23 19:52:25 stovepipebox ata4.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
Apr 23 19:52:25 stovepipebox ata4.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 23 19:52:25 stovepipebox ata4.00: configured for UDMA/133
Apr 23 19:52:25 stovepipebox scsi 2:0:0:0: Direct-Access ATA ST3120827AS 3.42 PQ: 0 ANSI: 5
Apr 23 19:52:25 stovepipebox scsi 3:0:0:0: Direct-Access ATA ST3320620AS 3.AA PQ: 0 ANSI: 5
This "model number mismatch 'ST3120827AS' != '3120827AS " looks like a result of a corrupted config (at least, I suspect so ). Any questions/suggestions?
Last edited by Llama (2008-05-02 20:20:04)

I had this same damn thing happen. The problem is in the way the kernel gets its info from the bios. The bios has a nasty habit of switching the drives around even when sda is connected to sata1. This became a problem when libata came about and changed all drives to sdxX naming convention.
To fix the no booting problem and the stupid rootfstype= error thing, u need to use Persistent block naming device scheme. Here on the wiki is a page dedicated to this... http://wiki.archlinux.org/index.php/Per … ice_naming
Try it and see if it helps. I used the /dev/by-uuid.

Windows has detected file system corruption on local disk. How can i solve this problem?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>chkdsk
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
4 percent complete. (148991 of 343808 file records processed)
Attribute record (128, "") from file record segment 154351
is corrupt.
4 percent complete. (157441 of 343808 file records processed)
Attribute record (128, "") from file record segment 165044
is corrupt.
Attribute record (128, "") from file record segment 170460
is corrupt.
5 percent complete. (171904 of 343808 file records processed)
Attribute record (128, "") from file record segment 176325
is corrupt.
Attribute record (128, "") from file record segment 176329
is corrupt.
Attribute record (128, "") from file record segment 176849
is corrupt.
343808 file records processed.
File verification completed.
3390 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
C:\Windows\system32>

well actually HP notebooks bioses have some diagnostics an user can run: HDD test, memory check, battery check thats all.
Still U can use HD Tune if U download it - freeware. But Hard Drive test U can do in Bios also works very well. I suggest this one cause when it detect something HP wont be oposing to U'rs repair request.
click on Kudos if i helped U

[SOLVED] /bin/tar: Cannot utime: Read-only file system

While doing a tar backup on my servers, I get this error:
/bin/tar: /usr/local/bin/sendEmail: Cannot utime: Read-only file system
The error happens on all files in /usr that I'm trying to backup. I know why the error is happening -- I deliberately mount /usr as read-only.
I'd like to know why tar is trying to "utime" my files and how I can stop that behaviour if possible?
This is my tar command:
tar cjf /mnt/backup/backup.tar.bz2 --label='backup_090116' --atime-preserve --no-wildcards-match-slash --files-from=/root/backup.include --exclude-from=/root/backup.exclude
TIA
Last edited by fukawi2 (2009-01-17 07:53:02)

Isn't it quite pointless to preserve timestamps on files from a filesystem on which timestamps aren't modified? Maybe tar tries to update the timestaps prior to archiving the file and is that giving troubles.

Wich file system is recomended for an usb key? [SOLVED]

Hi. I have an 8Gb USB Stick (USB key or pendrive).
I will use it to store my backups and ocassionaly to move some files between PCs. I don't use windows so i don't need niether want compatibility, so i don't want to use FAT32.
So, wich file system is recomended to use on an usb key??
Should i use ext3, reiserfs, xfs, jfs??? or maybe ext4???
Has any of them any implication with the lifetime of the usb?
Thanks
Last edited by Thalskarth (2009-02-12 03:05:33)

BoppreH wrote:Isn't there any chance that you might need to stick it at a Windows based computer?
I use it for backups, so i wont need it. i have another one much smaller for that cases
Xyne wrote:Wouldn't a journalling filesystem reduce the lifetime of the USB stick?
Wintervenom wrote:Go with ext2. You generally do not want a journaled filesystem on a Flash device. It may cut the device's lifespan by up to fifty percent or more.
I was afraid of something like that... thanks for the advice
so, ext2 would be the best option, wouldn't it?
Thanks to all for your help

[SOLVED] Fresh install read only file system

I just did a fresh install of Arch this morning, and I have been trying to fix it most of the day. I was following the Beginner's Guide in the wiki as close as I could. (There were a couple items that didn't quite match up.) I only edited the files that it told me to, and then just minor edits. I checked out /etc/fstab during the process and noticed that none of my hard drives were present. I didn't think this was normal, so I opened another terminal and grabbed the UUIDs with ls -l /dev/disk/by-uuid/. I have two hard drives, but only sda1 (/) and sda2 (swap) showed up. (sdb1 is the entire second hard drive as /home.) Here is the default fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
/dev/fd0 /media/fl auto user,noauto 0 0
The example documentation indicated that the file should have lines similair to...
/dev/disk/by-uuid/6334340b-87f1-406e-a777-13210ba85887 / ext3 defaults,noatime,nodirtime 0 1
/dev/disk/by-uuid/5ffd6a40-6d72-4710-82af-ae894e557f89 swap swap defaults 0 0
/dev/disk/by-uuid/32935c6c-6b75-4039-6b69-21f8b805e8f8 /home ext3 defaults,noatime,nodirtime 0 2
...but then I found an example while searching around that showed the lines like this:
UUID=6334340b-87f1-406e-a777-13210ba85887 / ext3 defaults,noatime,nodirtime 0 1
UUID=5ffd6a40-6d72-4710-82af-ae894e557f89 swap swap defaults 0 0
UUID=32935c6c-6b75-4039-6b69-21f8b805e8f8 /home ext3 defaults,noatime,nodirtime 0 2
In the first scenario, everything boots like normal, but when I tried to do anything that required writing to disk, the operation failed with a message about the file system being read-only. (I was trying to edit some config files because I couldn't get online.) Mind you, I was working as root the whole time, because I hadn't even gotten to adding a user yet. The only way I could make changes was to boot a live cd, mount, edit, reboot. remember to remove the live cd, reboot again, repeat.
In the second version of fstab, the bootup process kept trying to check the disk for errors. When it was done it wanted to reboot. Then it tried to check again (presumably because it couldn't save the fact that it had already checked).
I am at a loss. I really wish to use Arch Linux. I've been baby-fed for quite a while on Ubuntu, but it always ran slow. Please somebody help me! I am happy to provide more information; just let me know what you need.
Last edited by ravinggenius (2008-07-05 18:33:22)

Thank you so much for pointing out that typo! Turns out that is what was wrong. Well plus two of uuids had one typo each....
Also from what I can tell it doesn't matter which format I use for the uuids in fstab. I will use the UUID=xxxxx... version unless somebody can tell me why I shouldn't.

[Solved] Canot format MicroSD. File system is read-only

I formatted it for my special needs some time ago using fdisk.
Don't remember the partition table, but there was 1 fat32 and 1 ext4 partition.
Now I want to format it fat32 clean, but I get the errors.
When I open GParted, it says
GParted wrote:/dev/sdb contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?
If I click yes - it shows partitions, but creating new partition table fails, as it is read-only.
If I click no - it does not show up in the device list.
Here's a picture of the structure of the device.
What also strange, I remember making 1 GiB ext4, and rest fat32. But it shows the opposite.
So I tried formatting it with fdisk
$ fdisk /dev/sdb
o
n
w
fdisk: cannot write disk label: Bad file descriptor
I made sure they are unmounted
umount: /dev/sdb1: not mounted
umount: /dev/sdb2: not mounted
Then I checked the filesystems. The second one appears to be read-only
# fsck /dev/sdb1
fsck from util-linux 2.23.2
fsck.fat 3.0.22 (2013-07-19)
/dev/sdb1: 18 files, 96978/698280 clusters
# fsck /dev/sdb2
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-2013)
fsck.ext4: Read-only file system while trying to open /dev/sdb2
Disk write-protected; use the -n option to do a read-only
check of the device.
# fsck -n /dev/sdb2
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-2013)
/dev/sdb2: clean, 860/65664 files, 56633/262144 blocks
Tried the zero trick, but failed as well.
# dd if=/dev/zero of=/dev/sdb
dd: failed to open ‘/dev/sdb’: Read-only file system
# dd if=/dev/zero of=/dev/sdb2
dd: failed to open ‘/dev/sdb2’: Read-only file system
Tried to disable the write-protection
# hdparm -r0 /dev/sdb
/dev/sdb:
setting readonly to 0 (off)
readonly = 0 (off)
After that, fdisk still fails to format.
In Windows 8, it mounts only the fat32 part.
diskpart can't erase partition table as well.
Last edited by Doctor Drive (2013-10-09 08:28:13)

Finally I found the solution
MicroSD adapter has a "lock" feature.
When I inserted the adapter, the lock always triggered to locked state.
So I fixed it in unlocked state using the ducktape.
http://kb.sandisk.com/app/answers/detai … -or-locked

[Solved] Favorite File System

Similar Messages

Maybe you are looking for