kricker Posted January 27, 2009 Share Posted January 27, 2009 I am having some strange issues with unRAID/bubbRAID. bubbaQ has informed me I should fsck my flash drive. I'm new to Linux. I've googled around and read up on it. I don't quite understand it all. What I've done so far is try to unmount the flash drive. I get a message back that the drive is busy. From what little I understood about the fsck command the device needs to be unmounted to be checked. So do I need to boot from a live Cd and run a fsck from that? Link to comment
SSD Posted January 27, 2009 Share Posted January 27, 2009 The flash drive is not formatted with ReiserFS. You don't want to run reiserfsck on your flash drive. They are typically formatted FAT32 I think. You could try chkdsk or scandisk if you put it in your Windows box. UPDATE: Sorry for any confusion. I now see that BubbaQ was suggesting running "fsck" which I'm assuming will work on a FAT32 drive. Normally discussions of running "fsck" here mean the reiser flavor (because all of the disks are formatted that way EXCEPT the flash). Link to comment
bubbaQ Posted January 27, 2009 Share Posted January 27, 2009 1. Stop the array. 2. run the mount command to see what device the flash is (mounted on /boot) 3. umount the device. 4. fsck it. 5. reboot Link to comment
kricker Posted January 27, 2009 Author Share Posted January 27, 2009 Okay. I stopped the RAID but I still get a busy error: root@Tower:~# mount fusectl on /sys/fs/fuse/connections type fusectl (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sdc1 on /boot type vfat (rw,umask=000,shortname=mixed) /boot/bubba/portal/bubba_portal.fs on /var/www type ext3 (rw,loop=/dev/loop0) root@Tower:~# umount /dev/sdc1 umount: /boot: device is busy umount: /boot: device is busy root@Tower:~# Link to comment
bubbaQ Posted January 27, 2009 Share Posted January 27, 2009 I stopped the RAID but I still get a busy error: You didn't say you were running BubbaRaid.... it has other files open. After shutting down the array and all bubba apps, run: sync umount /boot/bubba/portal/bubba_portal.fs umount /dev/sdc1 Link to comment
kricker Posted January 27, 2009 Author Share Posted January 27, 2009 Sorry. I also tried without bubbaRAID and even though it didn't say anything was busy nothing seemed to happen. I'll try what you posted tonight. Link to comment
kricker Posted January 28, 2009 Author Share Posted January 28, 2009 I usually don't require so much hand holding I swear. but this is the result I got: root@Tower:~# sync root@Tower:~# umount /boot/bubba/portal/bubba_portal.fs root@Tower:~# umount /dev/sdc1 root@Tower:~# fsck /dev/sdc1 fsck 1.40.8 (13-Mar-2008) fsck: fsck.vfat: not found fsck: Error 2 while executing fsck.vfat for /dev/sdc1 root@Tower:~# I'm off to Google the error now. Link to comment
kricker Posted January 28, 2009 Author Share Posted January 28, 2009 dosfsck -av Dang your fast! I just got done doing dosfsck with a few different parameters seeing what it does. It found some issues and seems to have repaired them. Here is the result from dosfsck -av root@Tower:~# dosfsck /dev/sdc1 -av dosfsck 2.11 (12 Mar 2005) dosfsck 2.11, 12 Mar 2005, FAT32, LFN Checking we can access the last sector of the filesystem Boot sector contents: System ID "MSDOS5.0" Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 999424 bytes per FAT (= 1952 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 2015232 (sector 3936) 249736 data clusters (1022918656 bytes) 63 sectors/track, 255 heads 63 hidden sectors 2001825 sectors total Reclaiming unconnected clusters. Checking free cluster summary. /dev/sdc1: 2774 files, 44318/249736 clusters root@Tower:~# Link to comment
kricker Posted January 28, 2009 Author Share Posted January 28, 2009 Dang it! After all that something is still wrong.... As bubba knows I am doing this due to a crazy issue I am having running bubbaRAID. After getting dosfsck to run and I guess fix my drive, bubbaRAID still collapses on me. Here is what I did: Ran dosfsck and told it to repair. After that was done, I mounted the drive to /boot. Then I cd /bubba and ran rc.bubba. bubbaRAID came online and I went to update. I started the update. It got to about 6% then quit. Now /boot is no longer accessible thru putty. On the network the flash drive appears blank. None of the bubabRAID apps pages load. Should I format this Flash drive with a linux file system and install everything on that? Is this doable under unRAID? I figure since the OS is running in RAM I should be ale to format the drive mount it and copy the necessary files over. Link to comment
bubbaQ Posted January 28, 2009 Share Posted January 28, 2009 I would try a new flash. Link to comment
kricker Posted January 28, 2009 Author Share Posted January 28, 2009 I would try a new flash. Yes. I think its time I re-formated multiple times and the result is always the same. Link to comment
kricker Posted January 28, 2009 Author Share Posted January 28, 2009 New drive and all is well. Link to comment
jimwhite Posted January 28, 2009 Share Posted January 28, 2009 I wonder if it would be a good idea to have a place to list the Brand/Type of flash drives that people have had problems with... I've had similar problems with a Sandisk Cruiser/Micro 256mb. Yet I have a Sandisk Cruiser/Micro 512mb that's never given me a problem, though I've never used it as a boot drive. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.